Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1348

reference
38-tree-1
name
1348
tree-preservation-order

undefined

38-tpo-1
uprn
address-text
point
POINT (-1.025201 50.908646)
geometry
MULTIPOLYGON (((-1.025144 50.908640,-1.025147 50.908651,-1.025155 50.908661,-1.025167 50.908669,-1.025183 50.908674,-1.025200 50.908676,-1.025218 50.908675,-1.025234 50.908670,-1.025247 50.908662,-1.025255 50.908652,-1.025258 50.908641,-1.025256 50.908630,-1.025248 50.908620,-1.025235 50.908611,-1.025220 50.908606,-1.025202 50.908604,-1.025184 50.908606,-1.025168 50.908611,-1.025156 50.908619,-1.025147 50.908629,-1.025144 50.908640)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL